Distributed multi-datacenter video packaging system

ABSTRACT

A content streaming system and methodology for facilitating the management of content streaming. A video packaging and origination service requests streaming content that is organized according to content segments. Individual content segments will be encoded according to a plurality of encoding profiles and generated by different encoders. The video packaging and origination service utilizes synchronization information provided to the encoders to select individual encoded content segments responsive to the request for streaming content.

BACKGROUND

Generally described, computing devices and communication networks can beutilized to exchange data and/or information. In a common application, acomputing device can request content from another computing device viathe communication network. For example, a user at a personal computingdevice can utilize a browser application to request a content page(e.g., a network page, a Web page, etc.) from a server computing devicevia the network (e.g., the Internet). In such embodiments, the usercomputing device can be referred to as a client computing device and theserver computing device can be referred to as a content provider.

Content providers provide requested content to client computing devicesoften with consideration of efficient transmission of the requestedcontent to the client computing device and/or consideration of a costassociated with the transmission of the content. For larger scaleimplementations, a content provider may receive content requests from ahigh volume of client computing devices which can place a strain on thecontent provider's computing resources. Additionally, the contentrequested by the client computing devices may have a number ofcomponents, which can further place additional strain on the contentprovider's computing resources.

Some content providers attempt to facilitate the delivery of requestedcontent through the utilization of a content delivery network (“CDN”)service provider. As with content providers, CDN service providers alsoprovide requested content to client computing devices often withconsideration of efficient transmission of the requested content to theclient computing device and/or consideration of a cost associated withthe transmission of the content. Accordingly, CDN service providersoften consider factors such as latency of delivery of requested contentin order to meet service level agreements or the quality of deliveryservice.

BRIEF DESCRIPTION OF THE DRAWINGS

Throughout the drawings, reference numbers may be re-used to indicatecorrespondence between referenced elements. The drawings are provided toillustrate example embodiments described herein and are not intended tolimit the scope of the disclosure.

FIG. 1 is a block diagram of a content delivery environment thatincludes one or more user devices, a video packaging and originationservice and an original content provider according to one embodiment;

FIG. 2 is a block diagram of illustrative components of a user computingdevice configured to remotely process content in accordance with anillustrative embodiment;

FIG. 3 is a block diagram of illustrative components of an encodercomponent configured to generate encoded content according tosynchronization information in accordance with an illustrativeembodiment;

FIG. 4 is a block diagram of illustrative components of an ingress nodeconfigured to manage multiple encoder content streams in accordance withan illustrative embodiment

FIGS. 5A-5B are block diagrams of the content delivery environment ofFIG. 1 illustrating the interaction related to video packing andorigination service for obtaining encoded content for delivery to userdevices;

FIG. 6 is a flow diagram illustrative of a content processing routineimplemented by a video packaging and origination service; and

FIG. 7 is a flow diagram illustrative of a content processing routineimplemented by a content provider to generate multiple content streams.

DETAILED DESCRIPTION

Generally described, content providers can provide content to requestingusers. With regard to video content, a content provider can implement avideo packaging and origination service that is able to deliver videocontent to requesting users. Illustratively, a video packaging andorigination service indexes a collection of source video content (eitherlive streaming or file-based video-on-demand) and delivers it to clientsvia a wide range of communication protocols such as HTTP Live Streaming(“HLS”), Dynamic Adaptive Streaming over HTTP (“DASH”), HTTP DynamicStreaming (“HDS”), Real Time Messaging Protocol (“RTMP”), SmoothStreaming, and the like. Based on consumer demand, a video packaging andorigination service can also provide advanced video transmissionfeatures such as just-in-time packaging of video content, digital rightsmanagement (“DRM”) encryption, time-shifting, bitrate selection, catchup TV, and more.

To deliver content, content providers can organize requested content,such as a video file, into multiple segments that are then transmittedto requesting devices segment by segment. For example, in a videostream, each segment typically accounts for 2-10 seconds of videorendered on a receiving device. To provide content to the videopackaging and origination service, individual content segments can beencoded by an encoder and transmitted to the video and originationservice. Traditionally, a processing node on the video packaging andorigination service can receive an incoming stream of encoded segmentsand then transmit the stream to requesting user devices. Additionally,each distinct encoded video segment (e.g., combination of bitrateencoding and format) is provided to the video packaging and originationservice from a single encoder or encoding node.

Video segments can be encoded according to a defined bitrate and format,which generally defines the number of bits of data that are encoded overa measured amount of time and the specific software algorithm andresulting content representation format utilized to encode the data fortransmission. For video files, bitrates are typically measured accordingto how many kilobits or megabits of data are processed over a second oftime. By way of example, a data file that corresponds to 1 megabyte ofvideo data encoded in one second would be considered to have an encodingbitrate of 8 mbps (e.g., 8 megabits per second) while a lower definitionvideo file that corresponds to 45 kilobytes of video data processed inone second would be considered to have an encoding bitrate of 360 kbps(e.g., 360 kilobits per second).

To receive content, a client computing device can simply request contenthaving a fixed encoding rate or have a fixed encoding rate selected inresponse to a streaming content request. Such a fixed encoding rateapproach can be deficient in facilitating variance of the encodingbitrate (both positive and negative) based on factors, such as networkbandwidth, client computing device utilization, quality demands, and thelike. In addition to the association of the encoding bitrate, videosegments can be further defined by associating the encoding bitrate withthe encoding format utilized by the encoder to generate the outputstream. The encoding format can correspond to a content representationformat for storage or transmission of video content (such as in a datafile or bitstream). Examples of encoding formats include but not limitedto the motion pictures expert group (“MPEG) MPEG-2 Part 2, MPEG-4 Part2, H.264 (MPEG-4 Part 10), H.265 high efficiency video coding (“HEVC”),Theora, RealVideo RV40, VP9, and AOMedia Video 1 (“AV1”), and the like.Depending on the complexity of the encoding profiles specifying thebitrate and format, a single encoded may be constrained for more complexencoding profiles. This can limit the ability for content providers toprovide different encoding bitrate/format combinations or requireutilization of increased computing device resources to provide forindividual encoding nodes.

To address at least a portion of the inefficiencies described above withregard to single encoder transmission nodes, aspects of the presentapplication corresponding to a multi-encoder node system fortransmitting multiple encoder streams. More specifically, aspects of thepresent application correspond to utilization of synchronizationinformation to allow a video packaging and origination service toreceive multiple input streams corresponding to a set of contentsegments. Each individual stream can be provided by different encodersbased on the synchronization information, such as sequence referencenumbers or timestamp information. The number of encoders utilized by thecontent source, such as a content provider, may be based on thecomplexity of the encoding profile (e.g., encoded bitrate and format),available encoder computing resources, available network bandwidth,financial cost information, processing cost information and the like.

Using the synchronization information, the video packaging andorigination service can generate the set of encoded content byprocessing the multiple encoder streams and selecting encoded segmentsfrom different encoders. The video packaging and origination service canselect from duplicate encoding streams based on time received, qualitymeasurements, priority designations, attributable cost, or otherselection criteria. Additionally, in the event of a failure of one ofthe encoders, the video packaging and origination service can requestadditional encoders to complete the transmission or begin collectingadditional encoded segments from other encoders.

FIG. 1 illustrates a general content delivery environment 100 fordelivering content from original content providers to user devices. Thecontent delivery environment 100 includes a plurality of devices 102utilized by individual users, generally referred to as client computingdevices, to request streaming or download content from a video packagingand origination service 120. Illustratively, the video packaging andorigination service 120 indexes a collection of source video content(either live streaming or file-based video-on-demand) and delivers it toclients via a wide range of communication protocols such as HTTP LiveStreaming (“HLS”), Dynamic Adaptive Streaming over HTTP (“DASH”), HTTPDynamic Streaming (“HDS”), Real Time Messaging Protocol (“RTMP”), SmoothStreaming, and the like. Based on consumer demand, a video packaging andorigination service can also provide advanced video transmissionfeatures such as just-in-time packaging of video content, digital rightsmanagement (“DRM”) encryption, time-shifting, bitrate selection, catchup TV, and more. The content can be illustratively provided by one ormore origin sources, such as original content provider 130.

Client computing devices 102 may include any number of differentcomputing devices capable of communicating with the networks 140, 150,160, via a direct connection or via an intermediary. For example,individual accessing computing devices may correspond to a laptop ortablet computer, personal computer, wearable computer, server, personaldigital assistant (PDA), hybrid PDA/mobile phone, mobile phone,electronic book reader, set-top box, camera, appliance (e.g., athermostat or refrigerator), controller, watch, eyewear, a home or cardevice, Internet of Things (“IoT”) devices, virtual reality or augmentedreality devices, digital media player, and the like. Each clientcomputing device 102 may optionally include one or more data stores (notshown in FIG. 1) including various applications or computer-executableinstructions, such as web browsers, used to implement the embodimentsdisclosed herein. Illustrative components of a client computing device102 will be described with regard to FIG. 2.

In some embodiments, a CDN service provider 110 may include multipleedge locations from which a user device can retrieve content. Individualedge location 112 may be referred to herein as a point of presence(“POP”), where a POP is intended to refer to any collection of relatedcomputing devices utilized to implement functionality on behalf of oneor many providers. POPs are generally associated with a specificgeographic location in which the computing devices implementing the POPare located, or with a region serviced by the POP. As illustrated inFIG. 1, the POP 110 can include one or more metric informationprocessing component 114 for processing metric information provided byclient computing devices 102 and a data store 116 for maintain collectedmetric information. For example, a data center or a collection ofcomputing devices within a data center may form a POP. In someinstances, the POPs may implement one or more services, such as CDNservices, data storage services, data processing services, etc. The CDNservice provider 110 may include multiple POPs located in differentgeographic locations so that user devices can communicate with a nearbya POP to retrieve content, thereby reducing the latency of deliveringrequested content.

Networks 140, 150, 160 may be any wired network, wireless network, orcombination thereof. In addition, the networks 140, 150, 160 may be apersonal area network, local area network, wide area network, cablenetwork, fiber network, satellite network, cellular telephone network,data network, or combination thereof. In the example environment of FIG.1, network 140 is a global area network (GAN), such as the Internet.Protocols and components for communicating via the other aforementionedtypes of communication networks are well known to those skilled in theart of computer communications and thus, need not be described in moredetail herein. While each of the client computing devices 102 and videopackaging and origination service 110 are depicted as having a singleconnection to the network 140, individual components of the clientcomputing devices 102 and video packaging and origination service 110may be connected to the network 130 at disparate points. Accordingly,communication times and capabilities may vary between the components ofFIG. 1. Likewise, although FIG. 1 is illustrated as having threeseparate networks 140, 150, 160, one skilled in the relevant art willappreciate that the video packaging and origination service 110 mayutilize any number or combination of networks.

In accordance with embodiments, the video packaging and originationservice 120 includes one or more servers for receiving content fromoriginal content providers 130 and processing the content to makeavailable a set of received encoded bitrate segments. As described infurther detail below, the video packaging and origination service 120includes an ingress component 122 utilized to receive encoded datastreams from multiple encoding servers 132 from original contentproviders 130. The video packaging and origination service 120 canfurther include synchronization services 124 for generatingsynchronization information utilized by the encoders, such as sequencenumbers corresponding to the set of encoded segments, time stampinformation related to a relative time of the encoded segments or fromwhich relative time of encoded segments will be based, and the like. Thevideo packaging and origination service 120 can further include a datastore 126 for maintaining received encoded data for transmission.

It will be appreciated by those skilled in the art that the videopackaging and origination service 120 may have fewer or greatercomponents than are illustrated in FIG. 1. Thus, the depiction of thevideo packaging and origination service 120 in FIG. 1 should be taken asillustrative. For example, in some embodiments, components of the videopackaging and origination service 120 may be executed by one morevirtual machines implemented in a hosted computing environment. A hostedcomputing environment may include one or more rapidly provisioned andreleased computing resources, which computing resources may includecomputing, networking or storage devices. In another example, the videopackaging and origination service 120 can include one or more egresscomponents that can utilize the content received and processed from theingress component 122 and further process the content for transmissionto user devices 102. Such egress components may be implemented inconjunction with the ingress component 122, such as in a transcodingnode. In other embodiments, the egress components may be implemented andmanaged independently of the ingress components 122, such as in separatestand-alone computing devices.

With continued reference to FIG. 1, the content delivery environment 100also includes original content providers 130. Illustratively, theoriginal content provider can include a plurality of encoders 132 forgenerating multiple encoded streams for transmission to the videopackaging and origination service 120. The original content provider 130can also include logic or other management components for determininghow many encoders 132 should be utilized or how to manage the additionor removal of encoders. In some embodiments, the original contentprovider the original content provider 130 can further includesynchronization services 136 for generating synchronization informationutilized by the encoders, such as sequence numbers corresponding to theset of encoded segments, time stamp information related to a relativetime of the encoded segments or from which relative time of encodedsegments will be based, and the like. The video packaging andorigination service 120 can further include a data store 134 formaintaining encoded data for transmission. The synchronization services124 and 136 may work in conjunction or in a complimentary basis.

FIG. 2 depicts one embodiment of an architecture of an illustrative usercomputing device 102 that can generate content requests and processmetric information in accordance with the present application. Thegeneral architecture of the user computing device 102 depicted in FIG. 2includes an arrangement of computer hardware and software componentsthat may be used to implement aspects of the present disclosure. Asillustrated, the user computing device 104 includes a processing unit204, a network interface 206, an input/output device interface 209, anoptional display 202, and an input device 224, all of which maycommunicate with one another by way of a communication bus.

The network interface 206 may provide connectivity to one or morenetworks or computing systems, such as the network 140 of FIG. 1 and thevideo packaging and origination service 120 or the original contentprovider 130. The processing unit 204 may thus receive information andinstructions from other computing systems or services via a network. Theprocessing unit 204 may also communicate to and from memory 210 andfurther provide output information for an optional display 202 via theinput/output device interface 209. The input/output device interface 209may also accept input from the optional input device 224, such as akeyboard, mouse, digital pen, etc. In some embodiments, the usercomputing device 102 may include more (or fewer) components than thoseshown in FIG. 2.

The memory 210 may include computer program instructions that theprocessing unit 204 executes in order to implement one or moreembodiments. The memory 210 generally includes RAM, ROM, or otherpersistent or non-transitory memory. The memory 210 may store anoperating system 214 that provides computer program instructions for useby the processing unit 204 in the general administration and operationof the user computing device 102. The memory 210 may further includecomputer program instructions and other information for implementingaspects of the present disclosure. For example, in one embodiment, thememory 210 includes a network application 216, such as browserapplication or media player, for accessing content and communicatingwith the video packaging and origination service 120.

FIG. 3 depicts one embodiment of an architecture of an illustrativeserver for encoding content as described herein. The generalarchitecture of the encoder 132 depicted in FIG. 3 includes anarrangement of computer hardware and software components that may beused to implement aspects of the present disclosure. As illustrated, theencoder 132 includes a processing unit 304, a network interface 306, acomputer readable medium drive 308, an input/output device interface309, all of which may communicate with one another by way of acommunication bus. The components of the encoder 132 may be physicalhardware components or implemented in a virtualized environment.

The network interface 306 may provide connectivity to one or morenetworks or computing systems, such as the network 150 or network 160 ofFIG. 1. The processing unit 304 may thus receive information andinstructions from other computing systems or services via a network. Theprocessing unit 304 may also communicate to and from memory 310 andfurther provide output information for an optional display via theinput/output device interface 309. In some embodiments, the encoder 132may include more (or fewer) components than those shown in FIG. 3.

The memory 310 may include computer program instructions that theprocessing unit 304 executes in order to implement one or moreembodiments. The memory 310 generally includes RAM, ROM, or otherpersistent or non-transitory memory. The memory 310 may store anoperating system 314 that provides computer program instructions for useby the processing unit 304 in the general administration and operationof the video packaging and origination service 120. The memory 310 mayfurther include computer program instructions and other information forimplementing aspects of the present disclosure. For example, in oneembodiment, the memory 310 includes interface software 312 for receivingand processing content requests from the encoder 132. As will bedescribed in detail below, the resulting information can include adynamically configured bundle to encoding bitrates. Additionally, thememory 310 includes an encoder component 316 for processing contentsegments. Additionally, the encoder component 316 can further include asynchronization parameter component 318 for utilizing thesynchronization information in the encoding process to increase thelikelihood that encoded segments from multiple encoders can be utilizedby a video packaging and origination service 120.

FIG. 4 depicts one embodiment of an architecture of an illustrativeserver for functioning as an ingress component 122 as described herein.The general architecture of the ingress component 122 depicted in FIG. 4includes an arrangement of computer hardware and software componentsthat may be used to implement aspects of the present disclosure. Asillustrated, the ingress component 122 includes a processing unit 404, anetwork interface 406, a computer readable medium drive 408, aninput/output device interface 409, all of which may communicate with oneanother by way of a communication bus. The components of the ingresscomponent 122 may be physical hardware components or implemented in avirtualized environment.

The network interface 406 may provide connectivity to one or morenetworks or computing systems, such as the network 150 or network 160 ofFIG. 1. The processing unit 404 may thus receive information andinstructions from other computing systems or services via a network. Theprocessing unit 404 may also communicate to and from memory 410 andfurther provide output information for an optional display via theinput/output device interface 409. In some embodiments, the ingresscomponent 122 may include more (or fewer) components than those shown inFIG. 4.

The memory 410 may include computer program instructions that theprocessing unit 404 executes in order to implement one or moreembodiments. The memory 410 generally includes RAM, ROM, or otherpersistent or non-transitory memory. The memory 410 may store anoperating system 414 that provides computer program instructions for useby the processing unit 404 in the general administration and operationof the ingress node. The memory 410 may further include computer programinstructions and other information for implementing aspects of thepresent disclosure. For example, in one embodiment, the memory 410includes interface software 412 for receiving and processing contentrequests from the ingress component 122. As will be described in detailbelow, the resulting information can include a dynamically configuredbundle to encoding bitrates. Additionally, the memory 410 includes anencoder processing application 416 for processing incoming encodedcontent segments. Additionally, the ingress component 122 can furtherinclude a synchronization parameter component 418 for utilizing thesynchronization information in the encoding process to increase thelikelihood that encoded segments from multiple encoders can be utilizedby the ingress component 122.

At (1), the video packaging and origination service 120 can transmitsynchronization information to the original content provider 130.Illustratively, the synchronization information is utilized by multipleencoders 132 to allow encoded segments from multiple encoders to becombined seamlessly or substantially seamlessly. For example, thesynchronization information can include timestamp information related toa relative timestamp of individual encoded segments in the set ofencoded segments. In another example, the synchronization informationcan include sequence numbers for the individual segments. In anotherexample, the synchronization information can include a time of operationor other time elapsed information. The synchronization information isincorporated into the encoded segments and then utilized by the videopackaging and origination service 120 to assemble the set of orderedsegments, remove duplicates and identifying missing encoded segments.Although FIG. 5A illustrates the transmission of the synchronizationinformation from the video packaging and origination service 120, insome embodiments, synchronization information may not be transmitted bythe video packaging and origination service 120 and this interactionwould be omitted altogether.

At (2), the receiving original content provider 130 determines thenumber of encoders that will be utilized to generate the requestedencoded content streams. Illustratively, the determination the number ofencoders will generally corresponding to a plurality of encoders thatgenerate encoded content streams for identified requested content andincorporating synchronization information. In one embodiment, thedetermination of the number of encoders can be based on the complexityof the encoded bitrate and formation combination, available encoderresources, an attributable cost associated with the generated encodedcontent segments, preferences or service levels associated with thevideo packaging and origination service 120, network conditions (e.g.,available bandwidth, network throughput, error rates), demand from usersdevices (e.g., total number of requests or frequencies of requests), andthe like.

Illustratively, the content stream data may be transmitted by theoriginal content provider 130 responsive to a request from a user device102, a request from the video packaging and origination service 120, orother request/trigger. Illustratively, the encoded content cancorrespond to a set of encoded profiles corresponding to the encodingbitrate and format combinations that may be made available to users. Forexample, the video packaging and origination service 120 may provide arequesting user device 102 with a set of encoding bitrate and formatcombinations in order to support adaptive bitrate streaming.Accordingly, the request from the original content provider may transmitthe set of identified encoding bitrates and formats or individualencoding bitrate and format combinations to supplement previouslyreceive encoded segments. One skilled in the relevant art willappreciate that the transmission of the request or the identification ofrequested encoded segments (including format) can be facilitated in anumber of ways.

At (3), the original content provider causes the selected number ofencoders to generate encoded streams based on synchronizationinformation. As described above, the video packaging and originationservice 120 may provide the synchronization information. In anotherembodiment, the original content provider 130 can utilize self-providingsynchronization, information provided by a third-party service or acombination. At (4), the original content provider begins transmitting aplurality of encoded content streams to the video packaging andorigination service 120 and incorporating received/accessedsynchronization information. In some embodiments, the encoders 132B and132A are configured to transmit non-overlapping segments in which theencoding task for the set of segments it distributed among encoders. Inother embodiments, the encoders are configured to at least partiallytransmit overlapping or redundant encoded segments.

The video packaging and origination service 120 receives the pluralityof incoming encoded content streams from the encoders. At (5), the videopackaging and origination service 120 selects encoded segments from thereceived streams. Illustratively, if the encoded content streams arenon-overlapping, the video packaging and origination service 120 doesnot have to check for redundancies or other selection criteria (e.g.,time received or reputation of encoders). If the encoded content streamsmay have overlapping segments, the video packaging and originationservice 120 checks for redundancies or other utilizes selection criteriato determine which of the redundant encoded content segments will beutilized.

At (6), the video packaging and origination service 120 processes thereceived encoded segments. For example, the video packaging andorigination service 120 can be adjustments or error correction for anyof the selected encoded segments. In other embodiment, if thesynchronization information does not ensure perfectly compatible encodedsegments, the video packaging and origination service 120 canextrapolate additional segments or portions to facilitate combination.Still further, in some embodiments, the ingress component 122 of thevideo packaging and origination service 120 generates deterministic dataincluded in a set of meta-data utilized to access and generate outgoingcontent streams. Illustratively, the deterministic data can includetimestamp information related to a time of play of the set of encodedsegments, sequence number identifying an order of the encoded contentsegment in the set of encoded segments, a time of operation of theencoder and the like. In another example, the ingress component 122 orcontent management service 126 can conduct quality or error checkingthat can be included in meta-data. At (7) the video packaging andorigination service 120 stores the cumulative set of encoded segmentsfor delivery to user devices 102 along with any meta-data generated aspart of the processing.

Turning now to FIG. 5B, a fail over scenario will be described. Theinteractions illustrated in FIG. 5B are based interaction after theinitial transmission of multiple encoded segment transmission has begun.At (1), the original content provider 130 experiences an encoderfailure, generally illustrated as a failure to encoded component 132A.At (2), the original content provider continues transmitting a pluralityof encoded content streams to the video packaging and originationservice 120 and incorporating received/accessed synchronizationinformation. In some embodiments, if the encoders 132B and 132A werepreviously configured to transmit non-overlapping segments in which theencoding task for the set of segments it distributed among encoders, theoriginal content provider (via request or a priori) will be required toupdate the configuration of the remaining encoders 132 or to otherwisecause the initiation of additional encoders. In other embodiments, theencoders may be configured will at least partially overlapping encodedsegments. In this embodiment, the original content provider may notchoose to make any changes to the configurations.

At (3), the video packaging and origination service 120 receives theadjusted encoder node streams and processing the determine failover.Illustratively, the ingress component 122 may have specific rulesregarding failover, such as switching to a default encoder node or setof nodes. In other embodiments, the video packaging and originationservice 120 can request additional or alternative encoder nodes.Additionally, the video packaging and origination service 120 can scanfor already received encoded nodes received from the encoder prior tofailure and ensure that no additional errors were introduced prior tothe determined failure.

Turning now to FIG. 6, a routine 600 utilized by the video packaging andorigination service 120 to receive and process multiple encoder streamswill be described. Routine 600 may be illustratively implemented by aningress component 122.

At block 602, the video packaging and origination service 120 canoptionally transmit synchronization information to the original contentprovider 130. Illustratively, the synchronization information isutilized by multiple encoders 132 to allow encoded segments frommultiple encoders to be combined seamlessly or substantially seamlessly.For example, the synchronization information can include timestampinformation related to a relative timestamp of individual encodedsegments in the set of encoded segments. In another example, thesynchronization information can include sequence numbers for theindividual segments. In another example, the synchronization informationcan include a time of operation or other time elapsed information. Thesynchronization information is incorporated into the encoded segmentsand then utilized by the video packaging and origination service 120 toassemble the set of ordered segments, remove duplicates and identifyingmissing encoded segments. In embodiments in which the video packagingand origination service 120 does not transmit synchronizationinformation, such as if the original content provider 130 or otherservice provides the synchronization information, block 602 may beomitted.

Responsive to a request or trigger, as described above, the originalcontent provider 130 begins transmitting a plurality of encoded contentstreams to the video packaging and origination service 120 andincorporating received/accessed synchronization information at block604. In some embodiments, the encoders 132B and 132A may be configuredto transmit non-overlapping segments in which the encoding task for theset of segments it distributed among encoders. In other embodiments, theencoders may be configured will at least partially overlapping encodedsegments. At block 604, the video packaging and origination service 120receives the plurality of incoming encoded content streams from theencoders. At decision block 606, a determination is made as to whetheradditional encoder segments streams are received. If so, the routine 600returns to block 604 to receive the additional encoder streams. If not,the routine 600 proceeds to block 608.

At block 608, the video packaging and origination service 120 processesthe received encoded segments. For example, the video packaging andorigination service 120 can be adjustments or error correction for anyof the selected encoded segments. In other embodiment, if thesynchronization information does not ensure perfectly compatible encodedsegments, the video packaging and origination service 120 canextrapolate additional segments or portions to facilitate combination.Still further, in some embodiments, the ingress component 122 of thevideo packaging and origination service 120 generates deterministic dataincluded in a set of meta-data utilized to access and generate outgoingcontent streams. Illustratively, the deterministic data can includetimestamp information related to a time of play of the set of encodedsegments, sequence number identifying an order of the encoded contentsegment in the set of encoded segments, a time of operation of theencoder and the like. In another example, the ingress component 122 orcontent management service 126 can conduct quality or error checkingthat can be included in meta-data. At block 610, the video packaging andorigination service 120 stores the cumulative set of encoded segmentsfor delivery to user devices 102. As described above, the videopackaging and origination service 120 can also associate or storemeta-data associated with the segments. Routine 600 terminates at block612 or starts a new iteration of routine 600.

Turning now to FIG. 7, a routine 700 utilized by to generate multipleencoder streams will be described. Routine 700 may be illustrativelyimplemented by multiple encoder components 132. At block 702, theencoder component 132 (directly or indirectly) determines that anencoded content should be provided. Illustratively, the encoded contentcan correspond to a set of encoded profiles corresponding to theencoding bitrate and format combinations that may be made available tousers. For example, the video packaging and origination service 120 mayprovide a set of encoding bitrate and format combinations in order tosupport adaptive bitrate streaming. Accordingly, the content that willbe delivered to the video packaging and origination service 120 maycorrespond to the set of identified encoding bitrates and formats orindividual encoding bitrate and format combinations to supplementpreviously receive encoded segments. One skilled in the relevant artwill appreciate that the transmission of the request or theidentification of requested encoded segments (including format) can befacilitated in a number of ways.

At (2), the encoder can receive synchronization information or generatesynchronization information. As described above, the synchronizationinformation is utilized by multiple encoders 132 to allow encodedsegments from multiple encoders to be combined seamlessly orsubstantially seamlessly. For example, the synchronization informationcan include timestamp information related to a relative timestamp ofindividual encoded segments in the set of encoded segments. In anotherexample, the synchronization information can include sequence numbersfor the individual segments. In another example, the synchronizationinformation can include a time of operation or other time elapsedinformation. The synchronization information is incorporated into theencoded segments and then utilized by the video packaging andorigination service 120 to assemble the set of ordered segments, removeduplicates and identifying missing encoded segments.

At block 706, the receiving original content provider 130 determines thenumber of encoders that will be utilized to generate the requestedencoded content streams. Illustratively, the determination the number ofencoders will generally corresponding to a plurality of encoders thatgenerate encoded content streams for identified requested content andincorporating synchronization information. In one embodiment, thedetermination of the number of encoders can be based on the complexityof the encoded bitrate and formation combination, available encoderresources, an attributable cost associated with the generated encodedcontent segments, preferences or service levels associated with thevideo packaging and origination service 120, network conditions (e.g.,available bandwidth, network throughput, error rates), demand from usersdevices (e.g., total number of requests or frequencies of requests), andthe like.

At block 708, the original content provider causes the selected numberof encoders to generate encoded streams based on synchronizationinformation. As described above, the video packaging and originationservice 120 may provide the synchronization information. In anotherembodiment, the original content provider 130 can utilize self-providingsynchronization, information provided by a third-party service or acombination. At block 710, the original content provider beginstransmitting a plurality of encoded content streams to the videopackaging and origination service 120 and incorporatingreceived/accessed synchronization information. In some embodiments, theencoders 132B and 132A may be configured to transmit non-overlappingsegments in which the encoding task for the set of segments itdistributed among encoders. In other embodiments, the encoders may beconfigured will at least partially overlapping encoded segments. Routine700 terminates at block 712 or starts a new iteration of routine 700.

All of the methods and tasks described herein may be performed and fullyautomated by a computer system. The computer system may, in some cases,include multiple distinct computers or computing devices (e.g., physicalservers, workstations, storage arrays, cloud computing resources, etc.)that communicate and interoperate over a network to perform thedescribed functions. Each such computing device typically includes aprocessor (or multiple processors) that executes program instructions ormodules stored in a memory or other non-transitory computer-readablestorage medium or device (e.g., solid state storage devices, diskdrives, etc.). The various functions disclosed herein may be embodied insuch program instructions, or may be implemented in application-specificcircuitry (e.g., ASICs or FPGAs) of the computer system. Where thecomputer system includes multiple computing devices, these devices may,but need not, be co-located. The results of the disclosed methods andtasks may be persistently stored by transforming physical storagedevices, such as solid state memory chips or magnetic disks, into adifferent state. In some embodiments, the computer system may be acloud-based computing system whose processing resources are shared bymultiple distinct business entities or other users.

Depending on the embodiment, certain acts, events, or functions of anyof the processes or algorithms described herein can be performed in adifferent sequence, can be added, merged, or left out altogether (e.g.,not all described operations or events are necessary for the practice ofthe algorithm). Moreover, in certain embodiments, operations or eventscan be performed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors or processor cores or onother parallel architectures, rather than sequentially.

The various illustrative logical blocks, modules, routines, andalgorithm steps described in connection with the embodiments disclosedherein can be implemented as electronic hardware (e.g., ASICs or FPGAdevices), computer software that runs on computer hardware, orcombinations of both. Moreover, the various illustrative logical blocksand modules described in connection with the embodiments disclosedherein can be implemented or performed by a machine, such as a processordevice, a digital signal processor (DSP), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA) orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A processor device can be amicroprocessor, but in the alternative, the processor device can be acontroller, microcontroller, or state machine, combinations of the same,or the like. A processor device can include electrical circuitryconfigured to process computer-executable instructions. In anotherembodiment, a processor device includes an FPGA or other programmabledevice that performs logic operations without processingcomputer-executable instructions. A processor device can also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration. Although described herein primarily with respect todigital technology, a processor device may also include primarily analogcomponents. For example, some or all of the rendering techniquesdescribed herein may be implemented in analog circuitry or mixed analogand digital circuitry. A computing environment can include any type ofcomputer system, including, but not limited to, a computer system basedon a microprocessor, a mainframe computer, a digital signal processor, aportable computing device, a device controller, or a computationalengine within an appliance, to name a few.

The elements of a method, process, routine, or algorithm described inconnection with the embodiments disclosed herein can be embodieddirectly in hardware, in a software module executed by a processordevice, or in a combination of the two. A software module can reside inRAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory,registers, hard disk, a removable disk, a CD-ROM, or any other form of anon-transitory computer-readable storage medium. An exemplary storagemedium can be coupled to the processor device such that the processordevice can read information from, and write information to, the storagemedium. In the alternative, the storage medium can be integral to theprocessor device. The processor device and the storage medium can residein an ASIC. The ASIC can reside in a user terminal. In the alternative,the processor device and the storage medium can reside as discretecomponents in a user terminal.

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain embodiments include, whileother embodiments do not include, certain features, elements or steps.Thus, such conditional language is not generally intended to imply thatfeatures, elements or steps are in any way required for one or moreembodiments or that one or more embodiments necessarily include logicfor deciding, with or without other input or prompting, whether thesefeatures, elements or steps are included or are to be performed in anyparticular embodiment. The terms “comprising,” “including,” “having,”and the like are synonymous and are used inclusively, in an open-endedfashion, and do not exclude additional elements, features, acts,operations, and so forth. Also, the term “or” is used in its inclusivesense (and not in its exclusive sense) so that when used, for example,to connect a list of elements, the term “or” means one, some, or all ofthe elements in the list.

Disjunctive language such as the phrase “at least one of X, Y, or Z,”unless specifically stated otherwise, is otherwise understood with thecontext as used in general to present that an item, term, etc., may beeither X, Y, or Z, or any combination thereof (e.g., X, Y, or Z). Thus,such disjunctive language is not generally intended to, and should not,imply that certain embodiments require at least one of X, at least oneof Y, and at least one of Z to each be present.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it can beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As can berecognized, certain embodiments described herein can be embodied withina form that does not provide all of the features and benefits set forthherein, as some features can be used or practiced separately fromothers. The scope of certain embodiments disclosed herein is indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. A system to manage streaming content comprising: one or morecomputing devices associated with a video packaging and originationservice, wherein the video packaging and origination service isconfigured to: identify synchronization information corresponding to atleast one of segment sequence numbering or timestamp information; obtaina first plurality of segments of a set of segments from a first encodingnode of a plurality of encoding nodes; obtain a second plurality ofsegments of the set of segments from a second encoding node of theplurality of encoding nodes, the second encoding node different from thefirst encoding node, wherein segments from the first plurality ofsegments are interchangeable with segments from the second plurality ofsegments; process at least one segment from the first plurality ofsegments and at least one segment from the second plurality of segmentsto form the set of segments utilizing the synchronization information;and store the formed set of segments and meta-data associated with thestored set of segments.
 2. The system of claim 1, wherein the videopackaging and origination service transmits the at least one of segmentsequence numbering information or time stamp information to an originalcontent provider.
 3. The system of claim 1, wherein the video packagingand origination service transmits information that identifies a sourceof the at least one of segment sequence numbering information or timestamp information.
 4. The system of claim 1, wherein the first pluralityof segments and the second plurality of segments are based on costinformation associated with generating encoded segments.
 5. Acomputer-implemented method to manage transmission of contentcomprising: obtaining a first portion of a set of segments associatedwith a request for streaming content from a first identifiable encoder;obtaining a second portion of the set of segments associated with therequest for the streaming content from a second identifiable encoderdifferent from the first identifiable encoder, wherein at least aportion of the segments from the first and second portions areinterchangeable; and storing the set of segments based on a combinationof the first portion and the second portion.
 6. The computer-implementedmethod of claim 5 further comprising storing meta-data associated withthe combination of the first portion and the second portion.
 7. Thecomputer-implemented method of claim 5 further comprising transmitting arequest for synchronization information for utilization in the first andsecond portions of the set of segments.
 8. The computer-implementedmethod of claim 5, wherein the request for streaming content includescost selection information for use in determining the first portion andthe second portion.
 9. The computer-implemented method of claim 5further comprising processing the first portion and the second portionto form the set of segments.
 10. The computer-implemented method ofclaim 9, wherein processing the first and second portions to form theset of segments includes designating a default source of the set ofsegments.
 11. The computer-implemented method of claim 9, whereinprocessing the first and second portions to form the set of segmentsincludes selecting segments based on a time of receipt.
 12. Thecomputer-implemented method of claim 5 further comprising determining afailure in the first identifiable encoder.
 13. The computer-implementedmethod of claim 12 further comprising requesting at least one segmentfrom a third identifiable encoder responsive to the determined failureof the first identifiable encoder.
 14. The computer-implemented methodof claim 12, wherein storing the set of segments based on a combinationof the first portion and the second portion includes modifying the setof segments responsive to the determined failure.
 15. Acomputer-implemented method to manage transmission of contentcomprising: identifying streaming content, the streaming contentorganized according to a set of segments; selecting a number of encodersto provide requested content; and causing generation of a plurality ofencoder streams corresponding to the selected number of encoders toprovide the requested content, wherein encoded segments from theselected number of encoders are interchangeable to form a set of encodedcontent segments.
 16. The computer-implemented method of claim 15further comprising identifying synchronization information forutilization in the generation of the plurality of encoder streams. 17.The computer-implemented method of claim 15, wherein selecting a numberof encoders to provide the requested content includes selecting a numberof encoders based on a complexity associated with the requested content.18. The computer-implemented method of claim 15, wherein selecting anumber of encoders to provide the requested content includes selecting anumber of encoders based on a cost associated with the requestedcontent.
 19. The computer-implemented method of claim 15, furthercomprising determining a failure in an identifiable encoder.
 20. Thecomputer-implemented method of claim 19 further comprising selecting atleast one additional encoder to provide the requested content inresponse to the determined failure.